Network slice selection based on requested service

ABSTRACT

An example method can include receiving, from a user equipment, single-network slice selection assistance information (S-NSSAI). The method can include determining a resource sharing configuration (RSC) associated with the S-NSSAI and determining whether the S-NSSAI is associated with a network slice instance (NSI) of the network. When the S-NSSAI is determined to be associated with a first NSI, the method can include mapping the S-NSSAI to the first NSI to permit the user equipment to communicate via the first NSI using a protocol data unit (PDU) session associated with the S-NSSAI. When the S-NSSAI is not determined to be associated with an NSI, the method can include forming a second NSI of the network according to the RSC associated with the S-NSSAI and mapping the S-NSSAI to the second NSI to permit the user equipment to communicate via the second NSI using a PDU session associated with the S-NSSAI.

BACKGROUND

5G/New Radio (5G/NR) is a next generation global wireless standard.5G/NR provides various enhancements to wireless communications, such asflexible bandwidth allocation, improved spectral efficiency,ultra-reliable low-latency communications (URLLC), beamforming,high-frequency communication (e.g., millimeter wave (mmWave)), and/orthe like.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C is a diagram of an example implementation described herein.

FIG. 2 is a diagram of an example environment in which systems,functional architectures, and/or methods described herein can beimplemented.

FIG. 3 is a diagram of an example functional architecture of an examplecore network described herein.

FIG. 4 is a diagram of example components of one or more devices of FIG.2.

FIG. 5 is a flow chart of an example process for network slice selectionbased on a requested service.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings can identify the same or similar elements.

In a wireless telecommunications system (which can be referred to hereinas “the system”), such as a 5G wireless telecommunications network,network slicing allows for multiple virtual networks to run on a singlephysical network to support multiple services, applications, and/orentities (e.g., end users, customers, such as organizations that providea service to end users of the wireless telecommunications systems,and/or the like). In some instances, when a user equipment (UE) requestsa connection (e.g., protocol data unit (PDU) connectivity) to thenetwork for an application and/or service, the UE provides the networkwith information associated with the UE, the application, and/or theservice. Such information can include network slice selection assistanceinformation (NSSAI), which can include a collection or list ofindividual, single-network slice selection assistance information(S-NSSAI) (which can be referred to herein individually as “S-NSSAI” orcollectively as “S-NSSAIs”) that identify respective network slicesassociated with the UE. In such cases, a network slice selectionfunction (NSSF) of the system can determine a network slice instance(NSI) (e.g., a virtual network of network functions (NFs) and otherresources to support one or more S-NSSAIs) for the S-NSSAI. The NSSF canprovide, to an access and mobility management function (AMF), an NSIidentifier (NSI ID) associated with the NSI. Further, the AMF canidentify a session management function (SMF) to provision acommunication session of a network slice, using the corresponding NSI,for the UE. However, information elements of the S-NSSAI are not definedto enable the NSSF to select and/or determine an NSI based on certaincharacteristics of a communication session. According to previoustechniques, when determining the NSI, the NSSF might only consider aslice/service type (SST) of the S-NSSAI that identifies whether the UEis associated with an enhanced mobile broadband (eMBB) service, anultra-reliable, low-latency (URLLC) service, or a mobile Internet ofThings (mIoT) service.

Furthermore, the system can use a network slice subnet instance (NSSI)that can be shared by multiple NSIs. In other words, the NSSI can beconsidered a virtual network within a virtual network. However, thesystem does not define and/or set any relationships between the NSSIsand S-NSSAIs or enable the NSSF to use such relationships forservice-based network slice selection. In some cases, the NSSF canindicate, to the AMF, which set of S-NSSAIs a UE can be allowed to use.However, according to previous techniques, an NSSF of the system is notconfigured to determine an NSI for an S-NSSAI (e.g., processes and/ordata to perform the process cannot be defined to permit the NSSF todetermine the NSSI for an S-NSSAI).

Some implementations described herein enable an NSSF of a core networkof a telecommunications system (e.g., a 5G wireless telecommunicationsnetwork) to define information elements of an S-NSSAI to enable the NSSFto perform service-based NSI selection. Furthermore, someimplementations described herein can use NSSIs as resource sharingconfigurations (RSCs) and define a relationship between the S-NSSAI andan RSC. Moreover, some implementations described herein enable an NSSFto select and/or identify an NSI according to the RSC based on mappingsof the S-NSSAIs to NSIs and/or RSCs.

Accordingly, some implementations described herein enable an S-NSSAI tobe mapped to an NSI according to a service associated with the S-NSSAI.For example, as described herein, an NSSF can receive, from a UE, anS-NSSAI, determine a RSC associated with the S-NSSAI, and determine,based on the RSC, whether the S-NSSAI is associated with an NSI. If theNSSF determines that the S-NSSAI is associated with the NSI, the NSSFcan map the S-NSSAI to the NSI (e.g., using an unstructured data storagefunction (UDSF) of the core network). Additionally, or alternatively, ifthe NSSF determines that the S-NSSAI is not associated with the NSI, theNSSF can determine that a new NSI is to be formed, can cause an NSI tobe formed according to the RSC and map the S-NSSAI to the formed NSI. Inthis way, the NSSF can identify and/or associated an S-NSSAI to an NSIto permit the UE to engage in a PDU session associated with an S-NSSAI.

In this way, some implementations described herein permit service-basednetwork slicing. As described herein, an S-NSSAI can be used torepresent a type of a network slice that is to be used to create an NSIand/or can be used to identify an existing NSI. Furthermore, becausesome resources of a network can be shared, end-to-end, in a wirelesscommunication system, some resources can be dedicated to one or morecustomers based on a service level agreement (SLA) with the one or morecustomers. Accordingly, some implementations described herein permit anNSSF to define and form an NSI that incorporates flexible resourcesharing to meet objectives of various use cases, customers, and/or SLAs.Furthermore, some implementations described herein enable an NSSF tomake a deterministic selection of an NSI, from existing NSIs, accordingto an S-NSSAI to enable an NSSF to provide differentiation, deliverservices, and/or maintain SLAs. Therefore, the NSSF can associate anS-NSSAI with an NSI to ensure that network resources are efficientlyallocated for communication sessions involving one or more UEs and adata network, such that an adequate amount of resources are provided foreach communication session without overloading the network. Therefore,computing resources (e.g., processing resources and/or memory resources)associated with one or more components of a core network and/or networkresources (e.g., resource blocks) associated with the core network arenot wasted by over-allocating resources and/or under-allocatingresources for a communication session that uses an S-NSSAI.

FIG. 1A-1C are diagrams of an example implementation 100 describedherein. Example implementation 100 illustrates various portions of awireless telecommunications system (referred to herein as a “wirelessnetwork”), which in some implementations can be a 5G wirelesstelecommunications system. Example implementation 100 can be a 5Gwireless telecommunications system, a 4G wireless telecommunicationssystem, a long-term evolution (LTE) wireless telecommunications system,a LTE-Advanced (LTE-A) wireless telecommunications system, and/or thelike.

As shown in FIGS. 1A-1C, example implementation 100 can include a UEwirelessly connected to a radio access network (RAN) at a base station,which is connected to a data network via a core network. The UE can runan application that involves communicating with the data network, andtherefore the UE can enter into a communication session (e.g., a PDUsession) with the data network via the RAN and core network. The UE andthe core network can communicate application-specific data during thecommunication session. In some implementations, to permit the UE toenter into the communication session with the data network, the UE cansend an initial request to register with the core network.

The UE of example implementation 100 can be a communication and/orcomputing device, such as a mobile phone, a smartphone, a laptopcomputer, a tablet computer, an Internet of Things device, and/or thelike. The base station of example implementation 100 can include anaccess point of a RAN, such as a 5G next generation NodeB (gNodeB orgNB), a LTE evolved NodeB (eNodeB or eNB), and/or the like. In someimplementations, the base station facilitates a communication session bycommunicating application-specific data between the UE and the corenetwork.

The core network of example implementation 100 can include various typesof telecommunications core networks, such as a 5G next generation corenetwork (NG Core), an LTE evolved packet core (EPC), and/or the like. Asshown in FIGS. 1A-1C, the core network, among other components and/orfunctions, can include an access and mobility management function (AMF)component, a network slice selection function (NSSF) component, and anunstructured data storage function (UDSF) component of the corenetwork). In some implementations, the AMF, the NSSF, the UDSF and/orother components or functions, cannot be co-located or are notco-located (e.g., each component and/or function of the core network canbe at a different location from each other component and/or function ofthe core network).

The AMF of example implementation 100 can provide authentication and/orauthorization of the UE. In some implementations, an authenticationserver function (AUSF) component assists the AMF in authenticatingand/or authorizing the UE. Additionally, or alternatively, the AMF cancoordinate with a unified data management (UDM) component to obtainsubscribed NSSAI associated with the UE. The subscribed NSSAI caninclude a list of S-NSSAIs that the UE is subscribed to utilize (e.g.,for a communication session). In some implementations, the UE mayprovide a particular number of S-NSSAIs (e.g., eight S-NSSAIs or more,fifteen S-NSSAIs or more, and/or the like), within the NSSAI, whensending a UE configuration request. Therefore, the UE can provide theNSSAI to the AMF so that the UE can be associated with (e.g., registeredto, assigned to, and/or the like) an NSI, which can be considered avirtual network that is implemented through various physical resourcesof the RAN and/or network functions (NFs) of the core network. Asdescribed herein, the NSSF can provide an NSI for a S-NSSAIs included inthe NSSAI from the UE. For example, the NSSF can maintain a mapping ofS-NSSAIs to NSIs in the UDSF. In some implementations, the UDSF may bepart of the NSSF and/or co-located with the NSSF. Accordingly, the NSSFcan indicate an NSI selection and/or mapping of S-NSSAIs to NSIs to theAMF to permit the UE to utilize a corresponding NSI (and/or resources ofthe NSI) for a communication session.

In some implementations, the NSSF can determine a set of network slicepolicies to be considered when selecting an NSI. The set of networkpolicies can set rules and/or requirements at a network level (e.g., forall or a subset of UEs, for all or specific applications, for all orspecific geographic areas, and/or the like) and/or a user level (e.g.,per UE, per application, and/or the like). The set of network slicepolicies, which can be maintained by a policy control function (PCF)component of the core network, can include an area capacity policy(e.g., a data rate capacity over an area), a mobility policy (e.g.,location and speeds of UEs), a density policy (e.g., a number ofcommunications sessions over an area), a guaranteed minimum data ratepolicy (e.g., minimum download and upload speeds), a maximum bitratepolicy (e.g., maximum download and upload bitrates), a relative prioritypolicy (e.g., relative importance of the application and/or UE comparedto other applications and/or UEs), an absolute priority policy (e.g.,objective importance of the application and/or UE compared to otherapplications and/or UEs), a latency rate policy (e.g., an end-to-endcommunications transmission time), a reliability policy (e.g., acommunications transmission success rate), a resource scaling policy(e.g., an ability or range for scaling resources up or down), and/or thelike. In some implementations, the set of network slice policies candefine a low latency performance requirement (e.g., an end-to-endcommunications transmission time less than or equal to a threshold, suchas 10 ms), a high latency performance requirement (e.g., an end-to-endcommunications transmission time greater than a threshold, such as 10ms), a low reliability performance requirement (e.g., a communicationstransmission success rate less than a threshold, such as 99.99%), a highreliability performance requirement (e.g., a communications transmissionsuccess rate greater than or equal to a threshold, such as 99.99%), ahigh data rate performance requirement (e.g., download and upload speedsabove a threshold, such as 50 Mbps), a low data rate performancerequirement (e.g., download and upload speeds less than or equal to athreshold, such as 50 Mbps), a high traffic density requirement (e.g.,greater than or equal to a threshold number of user devices pergeographical area, such as 10,000 user devices per square kilometer),and/or a low traffic density requirement (e.g., less than a thresholdnumber of user devices per geographical area, such as 10,000 userdevices per square kilometer). In some implementations, the set ofnetwork slice policies can define a category for a service of acommunication session.

The data network of example implementation 100 can include various typesof data networks, such as the Internet, a third-party services network,an operator services network, a private network, a wide area network,and/or the like.

As shown in FIG. 1A, and by reference number 102, the UE can send a UEconfiguration request (e.g., a UE configuration message) (referred toherein as “the request”) to the base station of the RAN to register theUE with the network and/or initiate a communication session between theUE and the data network. As shown in FIG. 1A, the request can include anS-NSSAI. The S-NSSAI can be one of a plurality of S-NSSAIs in an NSSAIof the request. In some implementations, the request can identify thedata network (e.g., via a data network identifier) that is to beinvolved in a communication session with the UE. According to someimplementations, to send the request, the UE can run an application(e.g., a configuration application) that causes the UE to communicatewith the AMF of the core network, via the RAN, to request that anS-NSSAI associated with the UE be associated with an NSI to permit theUE to engage in a communication session with the data network.

In example implementation 100, the S-NSSAI can include service-basedinformation elements that permit the core network (e.g., the NSSF) toselect and/or associate the S-NSSAI with an NSI for the UE. Accordingly,the UE can utilize the NSI (as indicated by the NSSF and/or AMF, asdescribed herein) for a communication session associated with theS-NSSAI.

As shown in example implementation 100, the S-NSSAI of the request caninclude an SST field, a network slice type (NEST) field, a servicefield, an entity association field, and an inter-slice priority level(ISPL) field. In some implementations, the NEST, the service, the entityassociation, and the ISPL are included within a slice differentiator(SD) field of the S-NSSAI. According to some implementations, theS-NSSAI can be configured such that fields of the S-NSSAI are maintainedand/or identifiable by the UE, the RAN, the core network, and/or thelike. For example, the S-NSSAI can have a length of 32 bits, with 8 bitsbeing allocated for the SST and 24 bits being allocated for the SD, andeach information element of the SD can include a certain number of bitsand/or be included within the SD in a particular order or at particularlocations of the S-NSSAI. As described above, the SST can identify aservice/slice type (e.g., eMBB, URLLC, MIoT, and/or the like) for acommunication session involving the UE.

The NEST field of the S-NSSAI can include a NEST identifier thatidentifies a type of NSI that is capable of supporting one or moreapplications and/or services involved in a communication session thatuses the S-NSSAI to enable the UE to engage in the communicationsession. For example, the NEST can describe or identify a set ofcharacteristics that the NSI is to have to support a communicationsession associated with the S-NSSAI. In some implementations, suchcharacteristics can include a range of traffic quality of service (QoS)attributes (e.g., latency greater than a threshold number ofmilliseconds), resources and/or NFs associated with the communicationsession, resource scaling policies, a set of corresponding networkconfigurations, and/or the like. In some implementations, the NEST fieldcan include a NEST mapping for a particular SST. In other words, eachSST can have a unique mapping of NESTs. In some implementations, theNEST field can be allocated four bits of the SD.

The service field can include a service identifier that identifies oneor more services that can be involved in the communication session. Forexample, such services can include enhanced mobile broadband (e.g., forproviding enhanced broadband access in dense areas, ultra-high bandwidthaccess in dense areas, broadband access in public transport systems,and/or the like), connected vehicles (e.g., for providingvehicle-to-everything (V2X) communications, such as vehicle-to-vehicle(V2V) communications, vehicle-to-infrastructure (V2I) communications,vehicle-to-network (V2N) communications, and vehicle-to-pedestrian (V2P)communications, and/or the like), real-time service (e.g., for providinginter-enterprise communications, intra-enterprise communications, mapsfor navigation, and/or the like), enhanced multi-media (e.g., forproviding broadcast services, on demand and live TV, mobile TV,augmented reality (AR), virtual reality (VR), internet protocol (IP)multi-media subsystem (IMS) service, and/or the like), internet ofthings (IoT) (e.g., for providing metering, lighting management inbuildings and cities, environmental monitoring, traffic control, and/orthe like), URLLC (e.g., for providing process automation, automatedfactories, tactile interaction, emergency communications, urgenthealthcare, and/or the like), mission critical push-to-talk (PTT), afixed wireless access category (e.g., for providing localized networkaccess and/or the like), and/or the like. In some implementations, aservice type can be mapped to a same NEST. For example, IMS and Internetcan both be mapped to an eMBB NEST. In some implementations, the servicefield can be allocated seven bits of the SD.

The entity association field can include an entity identifier thatidentifies one or more entities that are associated with the serviceprovided in the communication session. For example, the one or moreentities can include one or more application service providers capableof communicating with an end user associated with the UE to provide theone or more services to the end user via a communication sessionassociated with the S-NSSAI. In some implementations, the one or moreentities can be configured to monitor (e.g., via the communicationsession) the services at a slice level. Accordingly, different entitiescan be associated with different policies (e.g., according to SLAs ofthe entities) that permit monitoring of the services at the slice level.In some implementations, an entity can be associated with and/orallocated an isolated network for services and/or operations of theentity (e.g., according to an SLA of the entity). In this way,entity-specific information can be included in an S-NSSAI to permit oneor more policies associated with the entity to be followed for acommunication session associated with the S-NSSAI. Accordingly, anentity can be assigned and/or be associated with specific S-NSSAIs thatcan be configured to be associated with specific NSIs, as describedherein. In some implementations, the entity association field can beallocated ten bits of the SD.

The ISPL field can include a priority identifier that identifies apriority level of an NSI that is to be selected for the S-NSSAI toensure that a priority, among network slices of the network, is given toa communication session associated with the S-NSSAI. As describedherein, traffic and services in one NSI should not impact traffic andservices of another NSI. However, if resources are limited, the ISPL canindicate which S-NSSAIs are to be prioritized over other S-NSSAIs.Contrary to previous techniques, which do not consider an inter-slicepriority for an S-NSSAI received from a UE, some implementationsdescribed herein can select an NSI for an S-NSSAI based on the ISPLidentified in the SD of the S-NSSAI. In this way, a communicationsession, when carried via an NSI and associated with the S-NSSAI, can begiven priority over other communication sessions that are using otherNSIs according to other S-NSSAIs that did not include such a priority(and vice versa). In some implementations, the ISPL field can beallocated four bits of the SD.

Additionally, or alternatively, an ISPL may be allocated or assigned toS-NSSAIs that do not include an SD. For example, an NSSF may use amapping of ISPLs for various SSTs of the S-NSSAIs. In this way, the NSSFmay be configured to determine an inter-slice priority for S-NSSAIsassociated with corresponding SSTs.

In this way, the UE can send an S-NSSAI (e.g., in a UE configurationrequest message) that includes information elements that permit the NSSFto make a service-based selection of an NSI.

As further shown in FIG. 1A, and by reference number 104, the RAN (e.g.,via the base station) can receive the request and perform an AMFselection process to identify the AMF of the core network that is to beused to set up a communication session (e.g., via an NSI) for the UEand/or register the UE with the network, as described herein. In someimplementations, the RAN can detect an identifier associated with the UE(e.g., an identifier that is mapped to an AMF, a temporary identifier ifthe UE is not registered with the UE, and/or the like) that can be usedto identify and/or select the AMF of the core network.

In some implementations, the AMF can be selected based on the S-NSSAIand/or an NSSAI associated with the S-NSSAI. For example, the RAN canidentify an SST of the S-NSSAIs in an NSSAI and select the AMF for theUE configuration according to a service/slice type of the S-NSSAIs. Inthis way, the RAN can forward the request and/or information in therequest (e.g., an NSSAI, including the S-NSSAI of FIG. 1A) to the AMF topermit the AMF to instruct the NSSF to identify an NSI for the S-NSSAIbased on the information elements of the S-NSSAI.

As further shown in FIG. 1A, and by reference number 106, the AMFperforms an authentication process and/or authorization processassociated with the UE. For example, the AMF can perform theauthentication process to authenticate the request and/or verify thatthe request was received from the UE identified in the request.Furthermore, the AMF can perform the authorization process to authorizethe UE to register and/or communicate as part of the wireless networkbased on the S-NSSAI and/or one or more other characteristics of the UE.

In some implementations, the AMF can utilize a lookup table to determinewhether to authenticate and/or authorize the UE. For example, the AMFcan compare the information that identifies the UE with informationaccessible to the AMF that identifies devices that are authorized toconnect with the wireless network (e.g., devices that subscribe to awireless network provider that maintains the wireless network, devicesthat are capable of communicating with a type of the wireless network,and/or the like). Once the AMF authenticates and/or authorizes the UE,the AMF can authorize the NSSF to determine an NSI for the S-NSSAI asdescribed herein.

In this way, the AMF can determine whether the UE is a valid device thatis capable of communicating over the wireless network and/or whether theUE has permission to connect with the data network (or RAN or corenetwork).

As further shown in FIG. 1A, and by reference number 108, the NSSFdetermines service-based network slice allocation for the S-NSSAI asdescribed herein. In some implementations, the NSSF determines an NSIand/or assigns the S-NSSAI to an NSI to allocate an NSI (e.g., alongwith corresponding resources or NFs of the NSI) to the S-NSSAI. Forexample, the NSSF can identify the information elements of the S-NSSAIto determine one or more characteristics of a communication sessionassociated with the S-NSSAI and select an NSI that can facilitate such acommunication session.

In some implementations, the NSSF can maintain one or more mappings(e.g., run-time tables) of S-NSSAIs associated with the wirelessnetwork. The one or more mappings can be maintained in the UDSF of thecore network. Such S-NSSAIs could have been issued to one or more otherUEs, could have been established by entities associated with theS-NSSAIs (e.g., when the entities entered into SLAs associated with thewireless network), and/or could have been previously provisioned by thewireless network to provide corresponding services associated with theS-NSSAIs. In some implementations, the NSSF can maintain an RSC mappingthat identifies RSCs of corresponding S-NSSAIs. In some implementations,the RSC mapping can include mappings of full S-NSSAIs or partialS-NSSAIs. For example, the NS SF can use a longest match analysis of areceived S-NSSAI as compared to one or more of the S-NSSAIs in the RSCmapping. In this way, the RSC mapping can determine that a partial matchof an S-NSSAI to an S-NSSAI in the RSC mapping (e.g., a match of the SSTand/or NEST) can be considered as a match or mapping for the receivedS-NSSAI. In some implementations, resource layers can be shared acrossS-NSSAIs with different SSTs and/or S-NSSAIs with different NESTs.Additionally, or alternatively, the NSSF can maintain one or moremappings of NSIs to the RSCs, NESTs, SSTs, and/or S-NSSAIs.

Accordingly, as described herein, when the NSSF receives an S-NSSAI, theNS SF can determine whether an RSC is associated with the S-NSSAI (e.g.,from a mapping of S-NSSAIs to RSCs). Additionally, or alternatively, asdescribed herein, the NSSF can determine whether the S-NSSAI isassociated with an NSI (e.g., from a mapping of RSCs and/or S-NSSAIs toNSIs). As described herein, the NSSF can utilize the one or moremappings to associate a received S-NSSAI with an NSI and/or identify anNSI that is to be used by a UE during a communication session associatedwith the S-NSSAI.

In FIG. 1B, the NSSF determines whether the S-NSSAI is to be associatedwith an RSC and/or an NSI using one or more mappings stored inassociation with the UDSF and/or maintained by the UDSF. As shown inexample implementation 100, the UDSF includes an RSC table and one ormore NSI runt-time tables. Each of the NSI run-time tables can beassociated with a particular SST. Therefore, as an example, a separateNSI run-time table (and thus separate values and/or variables) can bemaintained for an eMBB service of example implementation 100 versus anNSI run-time table maintained for a URLLC service of the wirelessnetwork of example implementation 100. In some implementations, one ormore processes illustrated in FIG. 1B can be performed in connectionwith the NSSF determining a service-based network slice allocation foran S-NSSAI, as described herein.

As shown in FIG. 1B, and by reference number 108 a, the NSSF determineswhether the S-NSSAI is associated with an RSC by determining whether theS-NSSAI is in an RSC table associated with the wireless network. The RSCtable can indicate resource layers that UEs associated with an S-NSSAIcan be configured to share with other UEs associated with otherS-NSSAIs. As used herein, a “first S-NSSAI sharing resources with asecond S-NSSAI” implies that UEs associated with the first S-NSSAI aresharing resources with UEs associated with the second S-NSSAI.

As shown in FIG. 1B, an RSC, which can be identified by an RSCidentifier (shown in the RSC table as RSC #), can include resourcelayers. For example, as shown, the RSCs of the RSC table can includefour resource layers (shown as RL-1 to RL-4). Each cell of the RSC tablein FIG. 1B identifies S-NSSAIs and whether the S-NSSAIs are to share theresources of the respective resource layer with other S-NSSAIs.Accordingly, each row of the RSC table identifies which S-NSSAIs areassociated with the RSC (e.g., RSC 0, RSC 1, RSC 2, RSC 3) of that rowand which S-NSSAIs of that RSC are to share resources of correspondingresource layers of the RSC with other S-NSSAIs. In some implementations,for a given RSC, one resource layer can be shared by all S-NSSAIsassociated with that RSC (e.g., assigned to have that RSC), or theresource layer can be dedicated to a single S-NSSAI.

In some implementations, an S-NSSAI is associated with only one RSC. Insome implementations, an RSC (e.g., RSC 0 of the RSC table) can be adefault RSC. Additionally, or alternatively, a default value (e.g., 0)for a particular cell of the RSC can be used to represent that resourcesof those resource layers, for that RSC, are to be shared by any or allS-NSSAIs in that cell. In some implementations, the S-NSSAIs of the RSCtable may be associated with any/all S-NSSAIs associated with a sameNEST. A default RSC can indicate that all resource layers of the RSC areto be shared by any or all S-NSSAIs that utilize the default RSC.

As an example, S-NSSAIs p, x, y, z are associated with RSC 1. In exampleimplementation 100, for RSC 1, S-NSSAIs x, y, z can be configured toshare resources of RL-3(as shown by “{x, y, z}”) and resources of RL-3are to be dedicated to S-NSSAI p. Therefore, as described herein, afirst NSI can be used for UEs associated with S-NSSAIs x, y, z to engagein a communication session and a second NSI, separate from the firstNSI, can be used for UEs associated with S-NSSAI p.

In some implementations, each of the resource layers can correspond toone or more NSSIs. For example, a sample NSSI stack can include resourcelayers corresponding to a core network NSSI (CN NSSI), a transportnetwork NSSI (TN NSSI), an access node central unit NSSI (RAN CU NSSI),an access node distributed unit NSSI (RAN DU NSSI), a radio resourceNSSI, and a carrier NSSI. In such a case, resources and/or functions ofthe CN NSSI can be included in a first resource layer of the RSC,resources and/or functions of the TN NSSI can be included in a secondresource layer of the RSC, and so on. Additionally, or alternatively,one or more of the above NSSIs can be considered to be within a sameresource layer of an RSC. For example, resources and/or functions of CNNSSI and TN NSSI can be in a first resource layer of an RSC and/orresources and/or functions of a radio resource NSSI and carrier NSSI canbe in a second resource layer of the RSC. Therefore, the resource layerscan be divided into one or more of carrier/band, radio frequencyresources, access node (AN) resources, TN resources, CN resources,and/or the like. In some implementations, each of these resources layerscan be further divided into more resource layers (e.g., for RL-specificscaling).

According to some implementations, if the received S-NSSAI is not in theRSC table (i.e., if the S-NSSAI is not one of S-NSSAIs a, m, n, p, x, y,or z), the NSSF can assign and/or determine that the S-NSSAI isassociated with a default RSC (e.g., RSC 0). On the other hand, if thereceived S-NSSAI is in the RSC table (i.e., if the S-NSSAI is one ofS-NSSAIs a, m, n, p, x, y, or z), the NSSF can determine the RSCassociated with the S-NSSAI and whether or not the S-NSSAI is configuredto share resources of any resource layers of the RSC.

In this way, the NSSF can identify an RSC associated with an S-NSSAI, topermit the RSC associated with the S-NSSAI to be associated with an NSIto permit the UE to use the NSI during a communication session with thedata network. In other words, the NSSF can determine whether services ofthe S-NSSAI indicate whether the UE is to use an NSI that allows forsharing of resources (e.g., of particular resource layers of an RSC)with UEs of other S-NSSAIs and/or whether the UE is to use an NSI thatallows for dedication of resources (e.g., of particular resources layersof an RSC) to UEs associated with that S-NSSAI.

As further shown in FIG. 1B, and by reference number 108 b, the NSSFdetermines whether the S-NSSAI is associated with an NSI by determiningwhether the RSC associated with the S-NSSAI is in one of the NSIrun-time tables. In some implementations, the NSI run-time table can bea microservice instantiated by the NSSF (or by an NSSF cloud-networkfunction (CNF)). According to some implementations, the NSSF canidentify an SST of the S-NSSAI, identify the NSI table for that SST, anddetermine whether the identified RSC, associated with the S-NSSAI andfrom the RSC table, is in that NSI run-time table.

In some implementations, the NSSF can build the NSI run-time tableaccording to the S-NSSAIs in the RSC table. For example, the NSSF canidentify whether there are any S-NSSAIs that are configured to havededicated resources of one or more of the resource layers of an RSC.More specifically, because two sets of S-NSSAIs (i.e., {x, y, z} and{p}) are associated with RSC 1 in example implementation 100, the NSSFcan determine that two separate NSIs are to be defined for each set. Inthis way, the resources of the respective NSIs for the RL-3 and RL-4 canbe separate from one another (e.g., mutually exclusive). Furthermore,two separate NSIs can be formed for RSC 3 (e.g., one NSI for S-NSSAI mand another NSI for S-NSSAI n) because the two NSIs are to have adedicated RL-4. As another example, RSC 2 can use a single for S-NSSAI jwith all resource layers being dedicated to S-NSSAI j. Finally, thedefault RSC is associated with all other S-NSSAIs or all other S-NSSAIsassociated with a same NEST.

According to some implementations, if the RSC is not in the NSI run-timetable (i.e., if the RSC is not one of RSC 0, RSC 1, or RSC 3), the NSSFcan form a new NSI (and/or cause a new NSI to be formed). For example,the NSSF can communicate with one or more components of the core network(e.g., a network function virtualization orchestration (NFVO) component)to create a new NSI. In such cases, a unique NSI identifier can beassigned to the new NSI and the S-NSSAI can be mapped to the new NSI inthe NSI run-time table. More specifically, if S-NSSAI j is received fromthe UE in example implementation 100, and RSC 2 from the RSC table, theNSSF can cause a new NSI to be created with NSI ID 23 (not shown), andS-NSSAI j can be assigned to use the NSI (e.g., via the NSI run-timetable). Additionally, or alternatively, if the RSC is not in therun-time table, the NSSF may determine that the S-NSSAI is to beassociated with a default NSI (e.g., a default NSI according to theNEST). Accordingly, the NSSF may map the S-NSSAI to the default NSIusing the UDSF, as described herein.

On the other hand, if the RSC is in the table, the NSSF can select theNSI for the S-NSSAI by finding the S-NSSAI in the NSI run-time table.For example, if S-NSSAI y is received from the UE in exampleimplementation 100, the NSSF can map the S-NSSAI to the NSI identifiedby NSI ID 2.

As mentioned above, the default RSC may be a default RSC for allS-NSSAIs, other than those specified in the RSC table, associated withthe wireless network. In some implementations, the SST and/or NEST isidentified when the RSC associated with the S-NSSAI is determined to bethe default RSC (e.g., RSC 0). For example, because the NEST can beunique within an SST and defines the type of an NSI for a communicationsession associated with the S-NSSAI, the NSSF can identify whether anNSI for the NEST exists when the RSC is the default RSC. Accordingly,although the RSC can be a default value, one or more unique NESTs can beused to determine whether an NSI is associated with the receivedS-NSSAI.

In some implementations, based on services associated with an S-NSSAI(e.g., as identified in the SST and/or SD of the S-NSSAI), the NSSF canassociate the S-NSSAI to an NSI to permit a UE to engage in acommunication session, via the NSI, according to the S-NSSAI associatedwith the UE. In this way, the NSSF can select an NSI that is availableand/or able to meet the characteristics of a service associated with thecommunication session, to permit the UE to receive the service.

As shown in FIG. 1C, and by reference 110, the NSSF indicates NSIinformation. For example, the NSSF can indicate the selected NSI to theAMF. As described herein, the NSSF can provide an identifier, from theNSI run-time table, for an NSI that is associated with the S-NSSAI.Additionally, or alternatively, the NSSF my indicate that the S-NSSAIhas been associated with the NSI and the AMF can use the NSI run-timetable to perform one or more operations associated with the indicatedNSI, as described herein. In this way, the NSSF can indicate, to theAMF, that the S-NSSAI has been associated with an NSI.

In some implementations, if the RSC is not in the NSI run-table and/orif the S-NSSAI is not in the NSI run-time table as described above inconnection with FIG. 1B, the NSSF can indicate that the S-NSSAI is notsupported and/or not allowed for use by the UE. Accordingly, the NSSF(and/or AMF) can deny the UE the capability to engage in a communicationsession using the S-NSSAI.

In some implementations, the NSSF may override the S-NSSAI. For example,based on a type of traffic of a communication session (e.g., a PDUsession) associated with the UE, the core network (e.g., via the NSSFand/or the AMF) may override the received S-NSSAI and assign an NSSAI tothe UE for the communication session. One or more S-NSSAIs of the NSSAImay then be used for the communication session.

As further shown in FIG. 1C, and by reference number 112, the AMF canprovision the UE to use the NSI. For example, the AMF can provision theUE to use the NSI in order to register the UE as part of the wirelessnetwork and/or enable the UE to engage in a communication session withthe data network via the NSI. In some implementations, the AMF, whenreceiving and/or sending messages (e.g., PDUs) from and/or to the UE,can use the physical resources associated with the NSI to permit themessages to be received or sent.

As further shown in FIG. 1C, and by reference number 114, the UE canengage in the communication session via the NSI.

In this way, some implementations described herein permit an NSSF toselect an NSI for an S-NSSAI, provided by a UE, to permit the UE toenter into a communication session with a data network associated withthe NSSF. The NSSF can select the NSI based on a service and/or acharacteristic of the UE, as defined by the S-NSSAI (e.g., in an SDfield), and RSCs associated with one or more NSIs of the network.Accordingly, some implementations described herein permit an NSSF, of acore network, to associate an S-NSSAI with an NSI that includes networkfunctions capable of providing a service of the S-NSSAI. Therefore, theNSSF can permit the UE to engage in a communication session with thedata network, using the S-NSSAI, to offer the services needed by the UE,and allow for efficient allocation of resources.

As indicated above, FIGS. 1A-1C are provided merely as an example. Otherexamples can differ from what is described with regard to FIGS. 1A-1C.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein can be implemented. As shown in FIG. 2,environment 200 can include a UE 210, an RAN 220, a base station 222, acore network 230, and a data network 240. Devices of environment 200 caninterconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

UE 210 can include one or more devices capable of communicating withbase station 222 and/or a network (e.g., data network 240). For example,UE 210 can include a wireless communication device, a radiotelephone, apersonal communications system (PCS) terminal (e.g., that can combine acellular radiotelephone with data processing and data communicationscapabilities), a smart phone, a laptop computer, a tablet computer, apersonal gaming system, user equipment, and/or a similar device. UE 210can be capable of communicating using uplink (e.g., UE to base station)communications, downlink (e.g., base station to UE) communications,and/or sidelink (e.g., UE-to-UE) communications. In someimplementations, UE 210 can include a machine-type communication (MTC)UE, such as an evolved or enhanced MTC (eMTC) UE. In someimplementations, UE 210 can include an Internet of Things (IoT) UE, suchas a narrowband IoT (NB-IoT) UE and/or the like.

RAN 220 can include a base station and be operatively connected, via awired and/or wireless connection, to the core network 230 through UPF324. RAN 220 can facilitate communication sessions between UEs and datanetwork 240 by communicating application-specific data between RAN 220and core network 230. Data network 240 can include various types of datanetworks, such as the Internet, a third-party services network, anoperator services network, a private network, a wide area network,and/or the like.

Base station 222 includes one or more devices capable of communicatingwith UE 210 using a cellular radio access technology (RAT). For example,base station 222 can include a base transceiver station, a radio basestation, a node B, an evolved node B (eNB), a gNB, a base stationsubsystem, a cellular site, a cellular tower (e.g., a cell phone tower,a mobile phone tower, etc.), an access point, a transmit receive point(TRP), a radio access node, a macrocell base station, a microcell basestation, a picocell base station, a femtocell base station, or a similartype of device. Base station 222 can transfer traffic between UE 210(e.g., using a cellular RAT), other base stations 222 (e.g., using awireless interface or a backhaul interface, such as a wired backhaulinterface), and/or data network 240. Base station 222 can provide one ormore cells that cover geographic areas. Some base stations 222 can bemobile base stations. Some base stations 222 can be capable ofcommunicating using multiple RATs.

In some implementations, base station 222 can perform scheduling and/orresource management for UEs 210 covered by base station 222 (e.g., UEs210 covered by a cell provided by base station 222). In someimplementations, base stations 222 can be controlled or coordinated by anetwork controller, which can perform load balancing, network-levelconfiguration, and/or the like. The network controller can communicatewith base stations 222 via a wireless or wireline backhaul. In someimplementations, base station 222 can include a network controller, aself-organizing network (SON) module or component, or a similar moduleor component. In other words, a base station 222 can perform networkcontrol, scheduling, and/or network management functions (e.g., forother base stations 222 and/or for uplink, downlink, and/or sidelinkcommunications of UEs 210 covered by the base station 222). In someimplementations, base station 222 can include a central unit andmultiple distributed units. The central unit can coordinate accesscontrol and communication with regard to the multiple distributed units.The multiple distributed units can provide UEs 210 and/or other basestations 222 with access to data network 240.

Core network 230 can include various types of core networkarchitectures, such as a 5G NG Core (e.g., core network 300 of FIG. 3),an LTE EPC, and/or the like. In some implementations, core network 230can be implemented on physical devices, such as a gateway, a mobilitymanagement entity, and/or the like. In some implementations, thehardware and/or software implementing core network 230 can bevirtualized (e.g., through the use of network function virtualizationand/or software-defined networking), thereby allowing for the use ofcomposable infrastructure when implementing core network 230. In thisway, networking, storage, and compute resources can be allocated toimplement the functions of core network 230 in a flexible manner asopposed to relying on dedicated hardware and software to implement thesefunctions.

Data network 240 includes one or more wired and/or wireless datanetworks. For example, data network 240 can include an IP MultimediaSubsystem (IMS), a public land mobile network (PLMN), a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a private network such as a corporate intranet, an ad hocnetwork, the Internet, a fiber optic-based network, a cloud computingnetwork, a third party services network, an operator services network,and/or the like, and/or a combination of these or other types ofnetworks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there can be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 can beimplemented within a single device, or a single device shown in FIG. 2can be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 can perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of an example functional architecture of a corenetwork 300 in which systems and/or methods, described herein, can beimplemented. For example, FIG. 3 can show an example functionalarchitecture of a 5G NG core network included in a 5G wirelesstelecommunications system. In some implementations, the examplefunctional architecture can be implemented by a core network (e.g., corenetwork 230 of FIG. 2) and/or one or more devices (e.g., a devicedescribed with respect to FIG. 4). While the example functionalarchitecture of core network 300 shown in FIG. 3 can be an example of aservice-based architecture, in some implementations, core network 300can be implemented as a reference-point architecture.

As shown in FIG. 3, core network 300 can include a number of functionalelements. The functional elements can include, for example, an NSSF 302,an AUSF 304, a UDM 306, a Network Resource Function (NRF) 308, an NEF310, an AF 312, an AMF 314, a UDSF 316, a PCF 318, a message bus 320, aSession Management Function (SMF) 322, and a UPF 324. These functionalelements can be communicatively connected via a message bus 320, whichcan be comprised of one or more physical communication channels and/orone or more virtual communication channels. Each of the functionalelements shown in FIG. 3 is implemented on one or more devicesassociated with a wireless telecommunications system. In someimplementations, one or more of the functional elements can beimplemented on physical devices, such as an access point, a basestation, a gateway, a server, and/or the like. In some implementations,one or more of the functional elements can be implemented on one or morecomputing devices of a cloud computing environment associated with thewireless telecommunications system. In some implementations, the corenetwork 300 can be operatively connected to an RAN 220, a data network240, and/or the like, via wired and/or wireless connections with UPF324.

NSSF 302 can select network slice instances for UEs, where NSSF 302 candetermine a set of network slice policies to be applied at the RAN 220.By providing network slicing, NSSF 302 allows an operator to deploymultiple substantially independent end-to-end networks potentially withthe same infrastructure. In some implementations, each slice can becustomized for different services. NEF 310 can support the exposure ofcapabilities and/or events in the wireless telecommunications system tohelp other entities in the wireless telecommunications system discovernetwork services and/or utilize network resources efficiently.

AUSF 304 can act as an authentication server and support the process ofauthenticating UEs in the wireless telecommunications system. UDM 306can store subscriber data and profiles in the wirelesstelecommunications system. UDM 306 can be used for fixed access, mobileaccess, and/or the like, in core network 230. PCF 318 can provide apolicy framework that incorporates network slicing, roaming, packetprocessing, mobility management, and/or the like.

AF 312 can determine whether UEs provide preferences for a set ofnetwork slice policies and support application influence on trafficrouting, access to NEF 310, policy control, and/or the like. AMF 314 canprovide authentication and authorization of UEs and mobility management.UDSF 316 includes one or more data structures configured to storeinformation, mappings, and/or the like associated with the core network300.

SMF 322 can support the establishment, modification, and release ofcommunication sessions in the wireless telecommunications system. Forexample, SMF 322 can configure traffic steering policies at UPF 324,enforce UE IP address allocation and policies, and/or the like. AMF 314and SMF 322 can act as a termination point for Non-Access Stratum (NAS)signaling, mobility management, and/or the like. SMF 322 can act as atermination point for session management related to NAS. RAN 220 cansend information (e.g., the information that identifies the UE) to AMF314 and/or SMF 322 via PCF 318.

UPF 324 can serve as an anchor point for intra/inter RAT mobility. UPF324 can apply rules to packets, such as rules pertaining to packetrouting, traffic reporting, handling user plane QoS, and/or the like.UPF 324 can determine an attribute of application-specific data that iscommunicated in a communication session. UPF 324 can receive information(e.g., information that identifies the communications attribute of theapplication) from RAN 220 via SMF 322 or an API. Message bus 320represents a communication structure for communication among thefunctional elements. In other words, message bus 320 can permitcommunication between two or more functional elements. Message bus 320can be a message bus, HTTP/2 proxy server, and/or the like.

The number and arrangement of functional elements shown in FIG. 3 areprovided as an example. In practice, there can be additional functionalelements, fewer functional elements, different functional elements, ordifferently arranged functional elements than those shown in FIG. 3.Furthermore, two or more functional elements shown in FIG. 3 can beimplemented within a single device, or a single functional element shownin FIG. 3 can be implemented as multiple, distributed devices.Additionally, or alternatively, a set of functional elements (e.g., oneor more functional elements) of core network 300 can perform one or morefunctions described as being performed by another set of functionalelements of core network 300.

FIG. 4 is a diagram of example components of a device 400. Device 400can correspond to UE 210, RAN 220, base station 222, and/or core network230. In some implementations UE 210, RAN 220, base station 222, and/orcore network 230 can include one or more devices 400 and/or one or morecomponents of device 400. As shown in FIG. 4, device 400 can include abus 410, a processor 420, a memory 430, a storage component 440, aninput component 450, an output component 460, and a communicationinterface 470.

Bus 410 includes a component that permits communication among thecomponents of device 400. Processor 420 is implemented in hardware,firmware, and/or a combination of hardware and software. Processor 420is a central processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 420includes one or more processors capable of being programmed to perform afunction. Memory 430 includes a random-access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 420.

Storage component 440 stores information and/or software related to theoperation and use of device 400. For example, storage component 440 caninclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid-state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 450 includes a component that permits device 400 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 450 caninclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 460 includes a component that providesoutput information from device 400 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 470 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 400 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 470 can permit device 400to receive information from another device and/or provide information toanother device. For example, communication interface 470 can include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a wireless local area network interface, a cellularnetwork interface, or the like.

Device 400 can perform one or more processes described herein. Device400 can perform these processes based on processor 420 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 430 and/or storage component 440. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions can be read into memory 430 and/or storagecomponent 440 from another computer-readable medium or from anotherdevice via communication interface 470. When executed, softwareinstructions stored in memory 430 and/or storage component 440 can causeprocessor 420 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry can be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 4 are provided asan example. In practice, device 400 can include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 4. Additionally, or alternatively, aset of components (e.g., one or more components) of device 400 canperform one or more functions described as being performed by anotherset of components of device 400.

FIG. 5 is a flow chart of an example process 500 for network sliceselection based on a requested service. In some implementations, one ormore process blocks of FIG. 5 can be performed by a component of a corenetwork (e.g., core network 230), such as by an NSSF (e.g., NSSF 302).In some implementations, one or more process blocks of FIG. 5 can beperformed by another device or a group of devices separate from orincluding an NSSF (e.g., NSSF 302), such as a UE (e.g., UE 210), an RAN(e.g., RAN 220), a base station (e.g., base station 222), or one or moreother components of the core network (e.g., an AUSF (e.g., AUSF 304), aUDM (e.g., UDM 306), an NRF (e.g., NRF 308), an NEF (e.g., NEF 310), anAF (e.g., AF 312), an AMF (e.g., AMF 314), a UDSF (e.g., UDSF 316), aPCF (e.g., PCF 318), a message bus (e.g., message bus 320), an SMF(e.g., SMF 322), a UPF (e.g., UPF 324), and/or the like).

As shown in FIG. 5, process 500 can include receiving, from a UE,single-network slice selection assistance information (S-NSSAI), whereinthe S-NSSAI is associated with a network (block 510). For example, theNSSF (e.g., using processor 420, memory 430, storage component 440,input component 450, communication interface 470, and/or the like) canreceive, from a UE, single-network slice selection assistanceinformation (S-NSSAI), as described above. In some implementations, theS-NSSAI is associated with a network.

As further shown in FIG. 5, process 500 can include determining aresource sharing configuration (RSC) associated with the S-NSSAI (block520). For example, the NSSF (e.g., using processor 420, memory 430,storage component 440, input component 450, communication interface 470,and/or the like) can determine an RSC associated with the S-NSSAI, asdescribed above.

As further shown in FIG. 5, process 500 can include determining, basedon the RSC associated with the S-NSSAI, whether the S-NSSAI isassociated with a network slice instance (NSI) of the network (block530). For example, the NSSF (e.g., using processor 420, memory 430,storage component 440, input component 450, communication interface 470,and/or the like) can determine, based on the RSC associated with theS-NSSAI, whether the S-NSSAI is associated with an NSI of the network,as described above.

As further shown in FIG. 5, process 500 can include mapping the S-NSSAIto the first NSI to permit the UE to communicate via the first NSI usinga protocol data unit (PDU) session associated with the S-NSSAI (block540). For example, when the S-NSSAI is determined to be associated witha first NSI, the NSSF (e.g., using processor 420, memory 430, storagecomponent 440, output component 460, communication interface 470, and/orthe like) can map the S-NSSAI to the first NSI to permit the UE tocommunicate via the first NSI using a PDU session associated with theS-NSSAI, as described above.

As further shown in FIG. 5, process 500 can include forming a second NSIof the network according to the RSC associated with the S-NSSAI (block550). For example, when the S-NSSAI is not determined to be associatedwith an NSI, the NSSF (e.g., using processor 420, memory 430, storagecomponent 440, input component 450, communication interface 470, and/orthe like) can form a second NSI of the network according to the RSCassociated with the S-NSSAI, as described above.

As further shown in FIG. 5, process 500 can include mapping the S-NSSAIto the second NSI to permit the UE to communicate via the second NSIusing a PDU session associated with the S-NSSAI (block 560). Forexample, the NSSF (e.g., using processor 420, memory 430, storagecomponent 440, output component 460, communication interface 470, and/orthe like) can map the S-NSSAI to the second NSI to permit the UE tocommunicate via the second NSI using a PDU session associated with theS-NSSAI, as described above.

Process 500 can include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the S-NSSAI is received in at least one of arequest from the user equipment to register the UE with the network or arequest to initiate the PDU session. In some implementations, a slicedifferentiator field of the S-NSSAI identifies at least one of: anetwork slice type (NEST) that identifies one or more characteristics ofthe network that are to be supported by the NSI, a service of thenetwork that is to be utilized by the UE, an entity associated with theUE, or an inter-slice priority level that identifies that an NSI that ismapped to the S-NSSAI has a priority relative to other NSIs of thenetwork.

In some implementations, the RSC identifies a set of resource layers, ofthe network, that the UE can share according to the S-NSSAI.

In some implementations, the NSSF, when determining the RSC, candetermine resource layers that can be shared with another UE associatedwith the S-NSSAI or another UE associated with another S-NSSAI. In someimplementations, the RSC is determined based on the resource layers.

In some implementations, the NSSF, when determining the RSC, candetermine that the S-NSSAI is not associated with a specific RSC, candetermine, based on the S-NSSAI not being associated with a specificRSC, that the S-NSSAI is associated with a default RSC, and candetermine that the RSC is the default RSC. In some implementations, theNSSF, when determining whether the S-NSSAI is associated with an NSI,can determine, based on the RSC being the default RSC, whether theS-NSSAI is associated with an NSI of the network based on at least oneof: a network service type (NEST) of the S-NSSAI or a service/slice type(SST) of the S-NSSAI. In some implementations, the NSSF can provisionthe PDU session, associated with the user equipment, to utilize thefirst NSI or the second NSI. In some implementations, the NSSF candetermine a traffic type of the PDU session, override, based on thedetermined traffic type of the PDU session, the S-NSSAI by assigning anNSSAI to the user equipment, and provision the PDU session according tothe assigned NSSAI.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 can include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 500 can be performed in parallel.

The foregoing disclosure provides illustration and description but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations can be made inlight of the above disclosure or can be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, canbe implemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features can be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below can directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems and can be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and can be used interchangeably with “one ormore.” Where only one item is intended, the phrase “only one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a device andfrom a user equipment, single-network slice selection assistanceinformation (S-NSSAI), wherein the S-NSSAI is associated with a network;determining, by the device, a resource sharing configuration (RSC)associated with the S-NSSAI; determining, by the device and based on theRSC associated with the S-NSSAI, whether the S-NSSAI is associated witha network slice instance (NSI) of the network; and when the S-NSSAI isdetermined to be associated with a first NSI, mapping, by the device,the S-NSSAI to the first NSI to permit the user equipment to communicatevia the first NSI using a protocol data unit (PDU) session associatedwith the S-NSSAI, or when the S-NSSAI is not determined to be associatedwith an NSI, forming, by the device, a second NSI of the networkaccording to the RSC associated with the S-NSSAI, and mapping, by thedevice, the S-NSSAI to the second NSI to permit the user equipment tocommunicate via the second NSI using a PDU session associated with theS-NSSAI.
 2. The method of claim 1, wherein the S-NSSAI is received in atleast one of: a request from the user equipment to register the userequipment with the network, or a request to initiate the PDU session. 3.The method of claim 1, wherein a slice differentiator field of theS-NSSAI identifies at least one of: a network slice type (NEST) thatidentifies one or more characteristics of the network that are to besupported by the NSI, a service, of the network, that is to be utilizedby the user equipment, an entity associated with the user equipment, oran inter-slice priority level that identifies that an NSI that is mappedto the S-NSSAI has a priority relative to other NSIs of the network. 4.The method of claim 1, wherein the RSC identifies a set of resourcelayers, of the network, that the user equipment can share according tothe S-NS SAL
 5. The method of claim 1, wherein determining the RSCcomprises: determining resource layers that can be shared with anotheruser equipment associated with the S-NSSAI or another user equipmentassociated with another S-NSSAI, wherein the RSC is determined based onthe resource layers.
 6. The method of claim 1, wherein determining theRSC comprises: determining that the S-NSSAI is not associated with aspecific RSC; determining, based on the S-NSSAI not being associatedwith a specific RSC, that the S-NSSAI is associated with a default RSC;and determining that the RSC is the default RSC, and wherein determiningwhether the S-NSSAI is associated with an NSI comprises: determining,based on the RSC being the default RSC, whether the S-NSSAI isassociated with an NSI of the network based on at least one of: anetwork service type (NEST) of the S-NSSAI, or a service/slice type(SST) of the S-NSSAI.
 7. The method of claim 1, further comprising atleast one of: provisioning the PDU session, associated with the userequipment, to utilize the first NSI or the second NSI, or determining atraffic type of the PDU session; overriding, based on the determinedtraffic type of the PDU session, the S-NSSAI by assigning network sliceselection assistance information (NSSAI) to the user equipment; andprovisioning the PDU session according to the assigned NSSAI.
 8. Adevice, comprising: one or more memories; and one or more processors,communicatively coupled to the one or more memories, to: receive, from auser equipment, single-network slice selection assistance information(S-NSSAI), wherein the S-NSSAI is associated with a network, determine aresource sharing configuration (RSC) associated with the S-NSSAI;determine, based on the RSC associated with the S-NSSAI, whether theS-NSSAI is associated with a network slice instance (NSI) of thenetwork; and when the S-NSSAI is determined to be associated with afirst NSI, map the S-NSSAI to the first NSI to permit the user equipmentto communicate via the first NSI using a protocol data unit (PDU)session associated with the S-NSSAI, or when the S-NSSAI is notdetermined to be associated with an NSI, form a second NSI of thenetwork according to the RSC associated with the S-NSSAI, and map theS-NSSAI to the second NSI to permit the user equipment to communicatevia the second NSI using a PDU session associated with the S-NSSAI. 9.The device of claim 8, the S-NSSAI is received in at least one of: arequest from the user equipment to register the user equipment with thenetwork, or a request to initiate the PDU session.
 10. The device ofclaim 8, wherein a slice differentiator field of the S-NSSAI identifiesat least one of: a network slice type (NEST) that identifies one or morecharacteristics of the network that are to be supported by the NSI, aservice, of the network, that is to be utilized by the user equipment,an entity associated with the user equipment, or an inter-slice prioritylevel that identifies that an NSI that is mapped to the S-NSSAI has apriority relative to other NSIs of the network.
 11. The device of claim8, wherein the RSC identifies a set of resource layers, of the network,that the user equipment can share according to the S-NSSAI.
 12. Thedevice of claim 8, wherein the one or more processors, when determiningthe RSC, are to: determine resource layers that can be shared withanother user equipment associated with the S-NSSAI or another userequipment associated with another S-NSSAI, wherein the RSC is determinedbased on the resource layers.
 13. The device of claim 8, wherein the oneor more processors, when determining the RSC, are to: determine that theS-NSSAI is not associated with a specific RSC; determine, based on theS-NSSAI not being associated with a specific RSC, that the S-NSSAI isassociated with a default RSC; and determine that the RSC is the defaultRSC, and wherein, the one or more processors, when determining whetherthe S-NSSAI is associated with an NSI, are to: determine, based on theRSC being the default RSC, whether the S-NSSAI is associated with an NSIof the network based on at least one of: a network service type (NEST)of the S-NSSAI, or a service/slice type (SST) of the S-NSSAI.
 14. Thedevice of claim 8, wherein the one or more processors are further to atleast one of: provision the PDU session, associated with the userequipment, to utilize the first NSI or the second NSI, or determine atraffic type of the PDU session; override, based on the determinedtraffic type of the PDU session, the S-NSSAI by assigning an NSSAI tothe user equipment; and provision the PDU session according to theassigned NSSAI.
 15. A non-transitory computer-readable medium storinginstructions, the instructions comprising: one or more instructionsthat, when executed by one or more processors, cause the one or moreprocessors to: receive, from a user equipment, single-network sliceselection assistance information (S-NSSAI), wherein the S-NSSAI isassociated with a network, determine a resource sharing configuration(RSC) associated with the S-NSSAI; determine, based on the RSCassociated with the S-NSSAI, whether the S-NSSAI is associated with anetwork slice instance (NSI) of the network; and when the S-NSSAI isdetermined to be associated with a first NSI, map the S-NSSAI to thefirst NSI to permit the user equipment to communicate via the first NSIusing a protocol data unit (PDU) session associated with the S-NSSAI, orwhen the S-NSSAI is not determined to be associated with an NSI, form asecond NSI of the network according to the RSC associated with theS-NSSAI, and map the S-NSSAI to the second NSI to permit the userequipment to communicate via the second NSI using a PDU sessionassociated with the S-NSSAI.
 16. The non-transitory computer-readablemedium of claim 15, the S-NSSAI is received in at least one of: arequest from the user equipment to register the user equipment with thenetwork, or a request to initiate the PDU session.
 17. Thenon-transitory computer-readable medium of claim 15, wherein a slicedifferentiator field of the S-NSSAI identifies at least one of: anetwork slice type (NEST) that identifies one or more characteristics ofthe network that are to be supported by the NSI, a service, of thenetwork, that is to be utilized by the user equipment, an entityassociated with the user equipment, or an inter-slice priority levelthat identifies that an NSI that is mapped to the S-NSSAI has a priorityrelative to other NSIs of the network.
 18. The non-transitorycomputer-readable medium of claim 15, wherein the RSC identifies a setof resource layers, of the network, that the user equipment can shareaccording to the S-NSSAI.
 19. The non-transitory computer-readablemedium of claim 15, wherein the one or more instructions, that cause theone or more processors to determine the RSC, cause the one or moreprocessors to: determine resource layers that can be shared with anotheruser equipment associated with the S-NSSAI or another user equipmentassociated with another S-NSSAI, wherein the RSC is determined based onthe resource layers.
 20. The non-transitory computer-readable medium ofclaim 15, wherein the one or more instructions, that cause the one ormore processors to determining the RSC, cause the one or more processorsto: determine that the S-NSSAI is not associated with a specific RSC;determine, based on the S-NSSAI not being associated with a specificRSC, that the S-NSSAI is associated with a default RSC; and determinethat the RSC is the default RSC, and wherein the one or moreinstructions, that cause the one or more processors to determine whetherthe S-NSSAI is associated with an NSI, cause the one or more processorsto: determine, based on the RSC being the default RSC, whether theS-NSSAI is associated with an NSI of the network based on at least oneof: a network service type (NEST) of the S-NSSAI, or a service/slicetype (SST) of the S-NSSAI.